Skip to content

provide permissions for 3-channel checks when called from deployment#64

Merged
MusicalNinjaDad merged 1 commit into
mainfrom
fix_3channel_checks
Apr 11, 2026
Merged

provide permissions for 3-channel checks when called from deployment#64
MusicalNinjaDad merged 1 commit into
mainfrom
fix_3channel_checks

Conversation

@MusicalNinjaDad
Copy link
Copy Markdown
Owner

No description provided.

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've left some high level feedback:

  • If only the called rust-stability.yml workflow needs these permissions, consider defining them in that reusable workflow under on.workflow_call.permissions instead of at the caller, so all callers share consistent permission requirements.
  • Double-check whether issues: write is strictly required for the quality-check job; if only read or no issues access is needed, reduce the permission scope accordingly to follow least-privilege principles.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- If only the called `rust-stability.yml` workflow needs these permissions, consider defining them in that reusable workflow under `on.workflow_call.permissions` instead of at the caller, so all callers share consistent permission requirements.
- Double-check whether `issues: write` is strictly required for the `quality-check` job; if only read or no issues access is needed, reduce the permission scope accordingly to follow least-privilege principles.

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@MusicalNinjaDad MusicalNinjaDad merged commit f127059 into main Apr 11, 2026
13 checks passed
@MusicalNinjaDad MusicalNinjaDad deleted the fix_3channel_checks branch April 11, 2026 17:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant